Merged
Conversation
github-actions
bot
force-pushed
the
release-elements-20260403065750775
branch
20 times, most recently
from
947093c to
dff52aa
Compare
github-actions
bot
force-pushed
the
release-elements-20260403065750775
branch
from
dff52aa to
8082961
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
⚠ NEVER add commits to this pull request.
🤖 This pull request was automatically created to facilitate human review of
@webref/elementschanges triggered by curated data at 1c0c5d7.🧐 Please review the diff below and version numbers. If all looks good, merge this pull request to release the changes to npm.
📦 Latest released
@webref/elementspackage was v2.7.0. Merging this pull request will release v2.7.1. Make sure that the bump is the right one for the changes.✍ If any change needs to be made before release, do not add a commit to this pull request. Changes should rather be handled in a separate pull request and pushed to the main branch. You may leave this pull request open in the meantime, or close it. The pre-release job will automatically update this pull request or create a new one once the updates have made their way to the main branch.
🛈 The actual change introduced by this pull request is a version bump in
packages/elements/package.json. You do not need to review that change. The bumped version is not the version that will be released when this pull request is merged, but rather the version that will be released next time.